|
The EFx Factory ((EFx Architectural-Guidance Software Factory )) is a pioneering Architectural Guidance Software Factory from Microsoft, and one of the first implementations of a software factory to be built. The ‘EFx Factory’ implements the (.NET Distributed Architecture ) for Service-Oriented applications and services. The factory is based upon an Architectural Application Framework called Enterprise Framework that describes a physical Microsoft .NET architecture leveraging Microsoft Enterprise Library and other service-oriented patterns from Microsoft patterns & practices. The EFX Factory was designed and built by development consultants within (Microsoft Consulting Services ) in response to customer demand for an implementation of the .NET Architecture, best practices for .NET development, and guidance on best use of Enterprise Library and a number of other application blocks freely available from Microsoft. ==History== Initially, (circa 2003, .NET Framework 1.0-1.1, Visual Studio 2002–2003) ‘Enterprise Framework’ (EFx) was built to meet growing customer demand for an implementation of the .NET architecture. The framework was based upon implementation patterns harvested from several enterprise solution implementations, for various customers. This framework implemented the layered .NET architecture and leveraged, and extended Enterprise Library to provide a complete framework for authoring applications and services on the .NET platform. This application framework evolved along with changes in the .NET platform, emerging Microsoft technologies and changes in industry service orientation patterns. The framework delivered a set of class libraries containing base implementations of the architectural layers prescribing certain technologies (such as ASMX), and ‘infrastructural services’ which developers used to address the cross-cutting concerns for the architectural layers: Exception handling, Authentication, Authorization, Logging etc. The framework extended Enterprise Library, and implemented several real-world security providers necessary for many customers of the time with heterogeneous technology environments. In addition, many best practice patterns, specifically concerning exception handling were built upon Enterprise Library to solve these requirements in an enterprise context. The framework also provided blocks that were not packaged in Enterprise Library, such as a validation block. It provided useful abstractions of Enterprise Library specific to this solution domain, that offered simplified APIs, and the framework unified the API with typing of string parameters. The framework was delivered (in source form) as a set of framework assemblies, packaged with Enterprise Library. The framework included a suggested set of solutions, Reference Implementation (RI) and documentation. From this, the developers created their client side applications and server side ASP.NET web services. Development of an application or service required a developer to create a new solution and implement a set of assemblies (one for each layer), that referenced the framework assemblies. These were then deployed as an executable application or web service. The primary challenge for developers was learning the patterns of the framework, and hand crafting the applications and services from blank solutions, without availability (at that time) of code templates. This resulted in prolific cut and pasting of code from the Reference Implementation code, itself highly vulnerable to manual error. Circa 2005, several technologies emerged from Microsoft that enabled the use of templates, automation and modeling of these types of applications and services, including: Visual Studio 2005, (Visual Studio Modeling ) (Distributed Application and System Designers), the (Guidance Automation Toolkit GAT ), and the (Domain-Specific Language Toolkit ) (DSL). Using these new technologies, the framework was able to evolve systematically into an implementation of a software factory. In that process, many of the constraints of the framework were lifted to enable further flexibility of the products which the factory could assemble. Primarily - the removal of the prescription of technology in the architectural layers, and the ability to deal effectively with change during the development of the applications and services. The factory introduced, through domain modeling, several new abstractions and utilized automation that were previously not possible. This factory was one of the first factories to combine DSL diagrams with GAT recipes, as well as extending the (Distributed Application and System Designers ) of Visual Studio with GAT recipes. The factory makes extensive use of recipes: for automating changes to solution structure and property changes to that structure, providing wizards to configure the models the factory provides, generating project templates for work products and automating menial tasks for the factory user. Circa 2006-2007, development on the EFx Factory was ceased as an offering from (Microsoft Consulting Services ), and many of the concepts it had pioneered are to be absorbed by the future software factory platform from Microsoft, and adopted by software factories from patterns & practices (such as the (Web Service Software Factory )). 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「EFx Factory」の詳細全文を読む スポンサード リンク
|